Skip to content

Extending test timeout for JS Extensions#1446

Open
aaronpowell wants to merge 1 commit into
mainfrom
javascript-ext-test-stability
Open

Extending test timeout for JS Extensions#1446
aaronpowell wants to merge 1 commit into
mainfrom
javascript-ext-test-stability

Conversation

@aaronpowell

Copy link
Copy Markdown
Member

On Windows, during local testing, these resources took a lot longer to start than expected, so extending the timeout

Closes #<ISSUE_NUMBER>

PR Checklist

  • Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
  • Based off latest main branch of toolkit
  • PR doesn't include merge commits (always rebase on top of our main, if needed)
  • New integration
    • Docs are written
    • Added description of major feature to project description for NuGet package (4000 total character limit, so don't push entire description over that)
  • Tests for the changes have been added (for bug fixes / features) (if applicable)
  • Contains NO breaking changes
  • Every new API (including internal ones) has full XML docs
  • Code follows all style conventions

Other information

On Windows, during local testing, these resources took a lot longer to start than expected, so extending the timeout
Copilot AI review requested due to automatic review settings June 30, 2026 06:56
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.sh | bash -s -- 1446

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.ps1) } 1446"

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Extends the startup/readiness wait timeout in the JavaScript Extensions integration test to accommodate slower resource startup (notably observed on Windows) when validating example apps in the Aspire distributed app host.

Changes:

  • Increased the WaitForResourceHealthyAsync(...).WaitAsync(...) timeout from 5 minutes to 10 minutes for the JavaScript Extensions AppHostTests readiness check.
Show a summary per file
File Description
tests/CommunityToolkit.Aspire.Hosting.JavaScript.Extensions.Tests/AppHostTests.cs Increases the resource health wait timeout used by the JavaScript Extensions AppHost integration test.

Review details

  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Low

var httpClient = fixture.CreateHttpClient(appName);

await fixture.ResourceNotificationService.WaitForResourceHealthyAsync(appName).WaitAsync(TimeSpan.FromMinutes(5));
await fixture.ResourceNotificationService.WaitForResourceHealthyAsync(appName).WaitAsync(TimeSpan.FromMinutes(10));
@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Code Coverage

Package Line Rate Branch Rate Complexity Health
CommunityToolkit.Aspire.Hosting.JavaScript.Extensions 92% 83% 190
Summary 92% (339 / 370) 83% (145 / 174) 190

@aaronpowell aaronpowell temporarily deployed to azure-artifacts July 3, 2026 03:41 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants